Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1216

reference
320-tree-1
name
1216
tree-preservation-order

undefined

320-tpo-1
uprn
address-text
point
POINT (-1.014664 50.865696)
geometry
MULTIPOLYGON (((-1.014607 50.865690,-1.014610 50.865701,-1.014618 50.865711,-1.014630 50.865719,-1.014646 50.865725,-1.014663 50.865726,-1.014681 50.865725,-1.014697 50.865720,-1.014710 50.865712,-1.014718 50.865702,-1.014721 50.865691,-1.014718 50.865680,-1.014711 50.865670,-1.014698 50.865662,-1.014682 50.865656,-1.014665 50.865655,-1.014647 50.865656,-1.014631 50.865661,-1.014619 50.865669,-1.014610 50.865679,-1.014607 50.865690)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL